Systems and methods to characterize units of work based on business objectives

ABSTRACT

Systems and methods for units of work based on business objectives are disclosed. Exemplary implementations may: manage environment state information maintaining a collaboration environment configured to facilitate interaction by users, the environment state information defining units of work and business objectives associated with the units of work; obtain progress information, the progress information for individual business objectives conveying progress toward fulfillment of the individual business objectives; update objective records for the business objectives based on the progress information so that the progress of the business objectives is maintained by the objective records; and/or perform other operations.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to characterize units of work based on business objectives.

BACKGROUND

Collaboration environments may enable users to assign projects, tasks, or other work to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which a virtual team of users does its work. A collaboration environment may enable users to work in a more organized and efficient manner. A collaboration environment may integrate features and/or functionality such as web-based conferencing and collaboration, desktop videoconferencing, and/or instant messaging into a single easy-to-use, intuitive interface.

SUMMARY

One aspect of the present disclosure relates to a system configured to characterize units of work based on business objectives. Within a collaboration environment, it may be important to set and organize business objectives, or goals, for users to work towards. Goals may be differentiated from tasks to complete a project because the goals may be expectations of outcomes and not merely user actions (i.e., tasks) to be completed. In some implementations, users may create business objectives that may be tracked to reflect progress towards fulfillment thereof. In some implementations, the progress may be updated based on monitoring of one or more of external resources, user input, and/or other information. The business objectives may be associated with a set of units of work that may indirectly facilitate progress toward fulfillment of the business objectives. The set of units of work may not directly contribute to the progress. By way of non-limiting illustration, a connection between the set of units of work and a corresponding business objective may be indirect in that completion of at least one of the units of work may have no direct impact on progress toward fulfillment of the business objective. The concept of “no direct impact” may mean that completion of the at least one unit of work may not cause progress toward fulfillment of the business objective without independent action outside of the at least one unit of work. Instead, the fulfillment of the at least one business objective may make such independent action more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, business objectives may be associated with a set of units of work that may directly facilitate progress toward fulfillment of the business objectives. Accordingly, completion of the set of units of work may directly contribute to the progress toward fulfillment.

In some implementations, business objectives may have one or more subordinate business objectives and/or one or more superior business objectives. The progress of a given business objective may directly and/or indirectly facilitate progress toward fulfillment of one or more superior business objectives. As such, the users may be able to view the progress, or lack thereof, towards fulfillment of the business objective and which units of works may be advantageous and which may be not.

By way of non-limiting illustration, a business objective may be to reach a given quantity of subscribers on a social media page. A set of units of work that may facilitate progress toward fulfillment of the business objectives may include a quantity of brand campaigns. Progress toward that fulfillment of the business objectives may not necessarily be achieving quantity of business campaigns, but rather it is reaching the desired outcome of the given quantity of subscribers. Thus, the business objective may be achieved while only one of the brand campaigns has happened—indicating a success- or may be missed even if all business campaigns are completed—indicating a failure. In this manner, a business objective may be a tool for leaders to set expectations of what outcomes they want to achieve, instead of merely what methods or work may be used to achieve them.

One or more implementations of a system to characterize units of work based on business objectives may include one or more hardware processors configured by machine-readable instructions. Executing the machine-readable instructions may cause the one or more hardware processors to facilitate characterizing units of work based on business objectives. The machine-readable instructions may include computer program components. The computer program components may include one or more of an environment state component, a progress component, a user interface component, and/or other components.

The environment state component may be configured to manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may define one or more of units of work assigned to individual users within the collaboration environment, business objectives associated with the units of work, and/or other information. The environment state information may include one or more of work unit records, objective records, and/or other records. The units of work may be specified within the work unit records. The business objectives may be specified within the objective records. Individual objective records may describe individual business objectives and may identify sets of individual ones of the work unit records that specify the units of work associated with the individual business objectives. By way of non-limiting illustration, a first objective record may describe a first business objective and identify a first set of work unit records that specifies a first set of units of work associated with the first business objective.

The progress component may be configured to obtain progress information and/or other information for individual ones of the business objectives. The progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. The progress toward fulfillment of the individual business objectives may be determined independently from incremental completion of the units of work in the individual sets of units of work associated with the individual business objectives. By way of non-limiting illustration, the connection between the set of units of work and a corresponding business objective may be indirect in that completion of at least one of the units of work may have no direct impact on progress toward fulfillment of the business objective. By way of non-limiting illustration, the progress information may convey the progress toward fulfillment of the first business objective. Completion of at least one of the units of work in the first set of units of work may have no direct impact on the progress toward fulfillment of the first business objective.

The progress component may be configured to update the objective records and/or the other records. The update may be based on the progress information and/or other information. As such, the progress toward fulfillment of the business objectives may be maintained by the objective records.

As used herein, any association (or relation, or reflection, or indication, or correspondency) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may include active and/or passive retrieval, determination, derivation, transfer, upload, download, submission, and/or exchange of information, and/or any combination thereof. As used herein, the term “effectuate” (and derivatives thereof) may include active and/or passive causation of any effect. As used herein, the term “determine” (and derivatives thereof) may include measure, calculate, compute, estimate, approximate, generate, and/or otherwise derive, and/or any combination thereof.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to characterize units of work based on business objectives, in accordance with one or more implementations.

FIG. 2 illustrates a method to characterize units of work based on business objectives, in accordance with one or more implementations.

FIG. 3 illustrates a graph of business objectives, in accordance with one or more implementations.

FIG. 4 illustrates a user interface, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to characterize units of work based on business objectives, in accordance with one or more implementations. In some implementations, users may create business objectives, or goals, that may be tracked to reflect progress towards fulfillment thereof. In some implementations, the progress may be updated based on monitoring of external resources, user input, and/or other information. The business objectives may be associated with a set of units of work that may facilitate the progress toward fulfillment but not directly contribute to the progress. In some implementations, the business objectives may have one or more of a subordinate business objective and/or a superior business objective.

In some implementations, system 100 may include one or more of one or more servers 102, one or more client computing platforms 104, external resources 126, and/or other components. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.

Server(s) 102 may include one or more of non-transitory electronic storage 128, one or more processors 130 configured by machine-readable instructions 106, and/or other components. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions 106 may cause server(s) 102 to facilitate characterizing units of work based on business objectives. The computer program components may include one or more of an environment state component 108, a progress component 110, a user interface component 112, and/or other instruction components.

Environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users within the collaboration environment. The environment state information may include one or more of user information, objective information, work information, and/or other information used to define, support, and/or otherwise maintain a collaboration environment.

The user information may include values of user parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters may include information describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user.

The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, a user role information, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more work unit records), one or more business objectives owned and/or managed by a user, one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records) assigned and/or managed by the user, one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given work unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), a presence parameter (e.g., indicating presence and/or interaction level at an environment level, unit of work level, project level, task level, application level, business objective level, etc.), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), one or more performance metrics of a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of work units, the efficiency of the user, bandwidth of the user, activity level of the user, how many business objectives the user has helped fulfill through their completion of units of work, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, schedule information, and/or other information

User role information may specify individual roles of the individual users in the individual units of work and/or business objectives. A role may represent a position of an individual user. The position may be specified based on a description of one or more of job title, level, stage, and/or other descriptions of position. The role may be specified with respect to a company as a whole, a particular unit of work, a particular business objective, and/or other considerations. By way of non-limiting illustration, a role may include one or more of chief executive officer (or other officer), owner, manager, supervisor, accountant, associate, employee, entry level, midlevel, senior, administrator, director, foreman, engineer, product developer, human resource officer, artist, art director, and/or other description.

The work information may include values of one or more work unit parameters. The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given work unit may have one or more assignees and/or team members working on the given work unit. Work units may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. Individual units of work may include one or more of an individual project, an individual task, an individual sub-task, and/or other units of work assigned to and/or associated with one or more users. An individual project may include a set of tasks and/or other information.

Individual sets of work unit records may be defined by a record hierarchy. A record hierarchy may convey individual positions of work unit records (and their corresponding units of work) in the record hierarchy. By way of non-limiting illustration, a position may specify one or more of a work unit record being superior to another work unit record, a work unit record being subordinate to another work unit record, and/or other information. As a result, individual work unit records in the individual sets of work unit records may be subordinate to other individual work unit records in the individual sets of work unit records. For example, a work unit record may define a unit of work comprising a task, and a subordinate work unit record may define a unit of work comprising a sub-task to the task. A record hierarchy may define a relationship between work unit records. A work unit record may have some restrictions placed on it by virtue of having a subordinate work unit record. By way of non-limiting illustration, a work unit record may be restricted from access by one or more users unless and/or until a subordinate work unit record is completed and/or started. In some implementations, the work unit records may include a first work unit record describing a first unit of work assigned to a first user and/or other work unit records. The first unit of work may include a first digital content item and/or other information.

Individual work units records may include hierarchical information defining a record hierarchy of the individual work unit records. The hierarchical information of a work unit record may include one or more of information identifying other work unit records associated in a record hierarchy the work unit record belongs to, a specification of the position of the work unit record in the hierarchy, restrictions and/or other relationships placed on the work unit record by virtue of its position, and/or other information.

In some implementations, as a consequence of the record hierarchies, the individual units of work described in the individual work unit records that are subordinate to the other individual work unit records may be subordinate to the individual units of work in the other individual work unit records.

In some implementations, the one or more work unit parameters may include one or more of a work assignment parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users.

In some implementations, the units of work may be described based on one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date, a completion date, and/or dates), one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, and/or other unit of work members and/or member information), a status parameter (e.g., an update, a hardcoded status update, a completed/incomplete/mark complete, a measured status, a status indicator, quantity of sub-work units remaining for a given unit of work, completed work units in a given project, and/or other status parameter), one or more user comment parameters (e.g., permission for who may make comments such as an assignee, an assignor, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters), one or more business objectives the unit of work is associated with, one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, given work unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more digital content item attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), hierarchical information, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.

The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or an other user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.

In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date).

The objective information may include values of one or more objective parameters. The values of the objective parameters may be organized in objective records corresponding to business objectives managed, created, and/or owned within the collaboration environment. Individual objective records may describe individual business objectives and identify sets of individual ones of the work unit records that specify the units of work associated with the individual business objectives. A given business objective may have one or more collaborators, and/or team members working on the given business objective. Business objectives may be created by a given user for the given user and/or created by the given user and assigned to be owned to one or more other users. Individual business objectives may include one or more of an individual goal, an individual sub-goal, and/or other business objectives assigned to be owned by a user and/or associated with one or more users. By way of non-limiting illustration, a first objective record may describe a first business objective and identify a first set of work unit records that specifies a first set of units of work associated with the first business objective.

In some implementations, business objectives may be derived from, and/or associated with, events and/or other information. The events may be external and/or integral to the collaboration environment. Events may include occurrences within an external resource (e.g., external resources 126) and/or occurrences in the real world.

External resources may include application programs accessible to the collaboration environment. An application program may be external to the collaboration environment and/or integrated into the collaboration environment. An application program external to the collaboration environment may be accessible by exiting (closing, minimizing, etc.) the environment and launching the application program separately. An application program integrated into the collaboration environment may be accessible within the environment and/or that access may not require leaving or exiting the environment. By way of non-limiting illustration, a business objective may be to reach a given quantity of subscribers on a social media page. The business objective may be derived from an event including a social media application showing subscribership to the social media page is reaching and/or exceeding the given quantity of subscribers. By way of non-limiting illustration, a business objective may be to increase the click-through-rate (CTR) on an ad on a webpage by a given percentage. The business objective may be derived from an event including an analytics program showing the CTR for the ad.

An occurrence within the real world may be determined through human observation with and/or without the assistance of a computer. By way of non-limiting illustration, a business objective may be to become more prominent in a given field of industry. The business objective may be derived from an event including the business being mentioned in an article written about the given field of industry. By way of non-limiting illustration, a business objective may be to onboard five new clients in a given month. The business objective may be derived from an event including observing the number of new clients being onboarded that given month. By way of non-limiting illustration, a business objective may be to increase the flow of foot traffic into a shop. The business objective may be derived from an event including observing the number of customers walking into the shop.

Individual sets of objective records may be defined by an objective record hierarchy. An objective record hierarchy may convey individual positions of objective records (and their corresponding business objectives) in the objective record hierarchy. By way of non-limiting illustration, a position may specify one or more of an objective record being superior to one or more other objective records, an objective record being subordinate to one or more other objective records, and/or other information. As a result, individual objective records may be subordinate and/or superior to other individual objective records. For example, the objective records may further include a second objective record. The first objective record and the second objective record may be organized by a first objective record hierarchy specifying that the second objective record is subordinate to the first objective record. Individual objective records may include hierarchical information defining an objective record hierarchy of the individual objective records. The hierarchical information of an objective record may include one or more of information identifying other objective records associated in an objective record hierarchy, a specification of the position of the objective record in the hierarchy, other relationships placed on the objective record by virtue of its position, and/or other information. In some implementations, as a consequence of the objective record hierarchies, the individual business objectives described in the individual objective records that are subordinate to the other individual objective records may be subordinate to the individual business objectives in the other individual objective records.

In some implementations, the one or more objective parameters may include one or more of an objective definition parameter, an objective progress parameter, and/or other parameters. The value of the objective definition parameter may describe a particular business objective. The values of an objective progress parameter may specify progress information for a particular business objective, and/or other information.

In some implementations, the business objectives may be described based on one or more of a business objective specification, one or more business objective dates (e.g., a start date, a due date, and/or dates), one or more members associated with a business objective (e.g., an owner, one or more other project/task members, member access information, and/or other business objective members and/or member information), one or more interaction parameters (e.g., indicating a given business objective was viewed, a given business objective was selected, how long the given business objective has been idle, a last interaction parameter indicating when and what user last interacted with the given business objective, users that interacted with the given business objective, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), notification settings, privacy, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), identification of units of work associated with a business objective, and/or other information.

A business objective specification may include one or more of what the business objective is (e.g., what is the desired outcome), an event associated with the business objective, an external resource associated with the business objective, and/or other information.

Progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. The progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. In some implementations, the progress toward fulfillment of the business objectives may be specified as one or more of a quantitative value, a qualitative value, and/or other information. In some implementations, the quantitative value may be a percentage of completion, an integer value, a dollar amount, and/or other values. In some implementations, progress toward fulfillment of the individual business objectives may be determined independently from incremental completion of the units of work in the individual sets of units of work associated with the individual business objectives. Meaning, the completion of the units of work associated with a given business objective may not directly progress the given business objective toward fulfillment, but completing the units of work may make accomplishing the business objective more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, progress toward fulfillment of the individual business objectives may be directly determined based on incremental completion of the units of work in the individual sets of units of work associated with the individual business objectives.

By way of non-limiting illustration, the progress information may convey the progress toward fulfillment of the first business objective. The progress toward fulfillment of the first business objective may be determined independently from the incremental completion of the units of work in the first set of units of work. In some implementations, the progress toward fulfillment of the business objectives may comprise progress toward occurrence of the events associated with the business objective.

The progress component 110 may be configured to obtain progress information and/or other information for individual ones of the business objectives. In some implementations, the progress component 110 may be configured to obtain the progress information by monitoring one or more external resources associated with the events. The progress component 110 may be configured to determine progress toward the occurrence of the events. Thus, responsive to determining progress toward the occurrence of the events, progress toward fulfillment of the business objectives may be determined.

In some implementations, progress component 110 may be configured to obtain progress information from user input and/or other information. The user input may be provided to specify the progress toward fulfillment of the business objectives. By way of non-limiting illustration, user input may be provided into a user interface. An input field within the user interface may be dedicated to obtaining the progress towards fulfillment of the business objective. The progress towards fulfillment of the business objective may include numbers and/or other values input within the quantity input field. In some implementations, the progress toward fulfillment of the business objectives may be based on one or more of an initial value, a target value, the user input, and/or other information. For example, upon the initial value being 0, the target value being 100, and the user input (obtained via the input field) being 11, a quantitative value of progress may be 11%. In some implementations, users may specify weights that different various pieces of information (e.g., project/portfolio/task completion) have on the fulfillment of a business objective. The weighted information may be aggregated to automatically calculate an overall progress. In some implementations, progress may track in a negative direction. By way of non-limiting illustration, a business objective may be to reduce churn from 4% to 3.5%. When you hit 3.75%, 50% progress toward the business objective has been made.

In some implementations, the progress component 110 may be configured to determine when the progress towards fulfillment of the individual business objectives is one or more of at, above, or below a progress threshold. The progress threshold may be a particular value of progress (e.g., expressed as an integer, a percentage of completion, and/or other values). In some implementations the progress threshold may be associated with a milestone. A milestone may include one or more of a particular date, completion of a particular amount of the units of work in the individual sets of units of work associated with the individual business objectives, and/or other milestones.

By way of non-limiting illustration, with respect to date milestones, a company may define business objectives around a “financial year” where they could have a “Q3 business objective”, where Q3 is defined by the organization with start and end dates that map to the company's financial year. The business objective due date may be separate from the date milestones, because not all “Q3” objectives are supposed to be done exactly at the last day of the quarter. While organizations commit to and review their Q3 objectives on the same cadence, some teams may have their Q3 objectives due in the middle and graded at the end.

In some implementations, the progress component 110 may be configured to correlate occurrence of the progress being at, above, or below the progress threshold with one or more units of work in the individual sets of units of work associated with the individual business objectives. For example, the progress toward fulfillment of a given business objective being at the progress threshold may be subsequent to completion of a subset of one or more units of work. Thus, the completion of the subset of one or more units of work may be correlated with the progress being at the progress threshold. For example, the progress toward fulfillment of a given business objective may be below a progress threshold by a given date. The completion of one or more units of work up to and including the given date may be correlated with the progress being below the progress threshold. By correlating the occurrence of the progress being at, above, or below the progress threshold with one or more units of work, users may be notified (see, e.g., user interface component 112) that their attempts to fulfill a given business objective may be successful or at risk. By way of non-limiting illustration, a business objective may be achieved while only a small number of units of work were completed—indicating a success—or may be missed even if all units of work are completed—indicating a failure. This may allow company leaders to get a perspective on progress toward business objectives, to allow them to prioritize the right work and seeing when and where business objectives are at-risk before it is too late. When a business objective is off track, teams may drill down into the strategy and/or units of work that may be causing this, helping them to take corrective action instantly.

In some implementations, a business objective may be “achieved” even if 100% of the progress was not. This may be important because some people follow the Objectives and key results (OKR) methodology where anything above 70% is considered “achieved” or you may determine that the “spirit” of the goal was achieved even though the metric wasn't quite hit.

In some implementations, user interface component 112 may be configured to effectuate presentation of individual user interfaces on individual client computing platforms of one or more client computing platforms 104. The user interface component 112 may be configured to effectuate presentation of a user interface displaying one or more of units of work, business objectives, and/or other information. In some implementations, the user interface may display representations of the business objectives in a timeline, list, flow chart, branching tree structure, directed acyclic graph (DAG), and/or other representations. In some implementations, the user interface may display representations of the business objectives and/or associated units of work in an ordered list. In some implementations, representations of the business objectives may include icons, graphics, and/or other elements. Selection of a representation of the business objectives may facilitate generating and presenting other views of the business objectives.

The user interface may include one or more user interface elements configured to facilitate user interaction with the user interface. By way of non-limiting illustration, user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other elements configured to facilitate user interaction.

A user interface may be configured to obtain user input comprising user entry and/or selection of business objectives, specification of information about the business objectives, provide updates to the progress toward fulfillment of the business objectives, and/or other information.

In some implementations, the user interface may display views of the individual objective records and/or other records. The views of the individual objective records may include descriptions of the individual business objectives, representations of the individual sets of units of work associated with the individual business objectives, a status indicator for the individual business objectives, and/or other views. The representations of the individual sets of units of work associated with the individual business objectives may include a link, a URL, a pointer, and/or other techniques to provide access to the units of work in the individual sets.

The status indicator may convey the progress toward fulfillment of the individual business objectives. In some implementations, the status indicator may display text such as “On Track”, “At Risk”, or “Off Track” and/or other indicia to convey a status of the business objective being fulfilled. In some implementations, the text and/or other indicia to convey the status may be individual particular colors associated with different statuses. For example, green may be associated with progress toward fulfillment of the business objective being on track and thus may be the color of the “On Track” text. The status indicator may display a progress bar that visualizes the progress towards fulfillment of the individual business objectives. In some implementations, the progress bar may comprise a particular color.

In some implementations, the user input into the user interface may include values for progress toward fulfillment of a given business objective. The values may be one or more of a percentage, a number, a currency (e.g., USD, EUR, JPY, GBP, CAD, AUD, etc.), and/or other formats of which the business objective is progressing. A target value may be a value at which progress towards fulfillment of the business objective concludes (e.g., business objective is fulfilled). An initial value may be a value at which the progress towards fulfillment of the given business objective should begin. For example, upon the initial value being 10 and the target value being 100, beginning of the progress may be 0. The initial value and the target value in the format may include no decimal places or more than one decimal place up to a maximum decimal place.

In some implementations, the user interface component 112 may be configured to generate one or more notifications. The notifications may include identification of the one or more units of work correlated with the occurrence of the progress being at or below the progress threshold. In some implementations, the notifications may include suggestions related to the one or more units of work. For example, the suggestion may include reevaluating the individual sets of units of work associated with the individual business objectives (or part thereof), replicating the individual sets of units of work (or part thereof), reassigning the individual sets of units of work (or part thereof) to other users, and/or other suggestions. The user interface component 112 may be configured to present the notifications. The notifications may be presented via the user interface.

The progress component 110 may be configured to update the objective records and/or the other records. The update may be based on the progress information and/or other information. As such, the progress of the business objectives may be maintained by the objective records. Simultaneously, the views of the individual objective records may be updated and displayed via the user interface accordingly. The views of the individual objective records that may be updated may include the status indicator, and/or other parts of the views.

In some implementations, environment state information may be updated as users continue to interact with the collaboration environment over time. The environment state component 108 may store and/or archive the environment state information periodically and/or based on user request to archive. In some implementations, the environment state component 108 may store historical environment state information specifying historical user information, historical work information, historical progress information, and/or other information.

FIG. 3 illustrates a directed acyclic graph 300 of business objectives in one or more objective record hierarchies, in accordance with one or more implementations. Graph 300 may demonstrate that business objectives may have more than one superior and/or subordinate business objective. Graph 300 may include Goal 1 and Goal 2. Goal 1 may be unrelated to Goal 2. Goal 1 and 2 may individually include one or more sub-goals. Goal 1 may include Sub-Goal A. Goal 2 may include Sub-Goal B. Goal A may include Sub-Goal C, D, and E. Progress toward fulfillment of Sub-Goals C, D, and E may directly and/or indirectly facilitate progress toward fulfillment of Sub-Goal A. The progress toward fulfillment toward Sub-Goal A may directly and/or indirectly facilitate progress toward fulfillment of Goal 1 and Goal 2 simultaneously.

FIG. 4 illustrates user interface 400, in accordance with one or more implementations. The user interface 400 may include a view showing a Sub-Goal A. The user interface 400 further shows a status indicator 402, status indicator 404, a quantitative value 406 of progress of Sub-Goal A, and sub-goals 408 of Sub-Goal A. Status indicator 402 may display a status of Sub-Goal A. Status indicator 404 may display a visual progress toward fulfillment of Sub-Goal A. Quantitative value 406 may further display the progress toward fulfillment of Sub-Goal A. Status indicator 402, status indicator 404, and quantitative value 406 may be updated based on monitoring progress toward occurrences of events external to a collaboration environment and/or based on user input. The user input may be entered via a user interface responsive to selection of user interface element 410. User interface 400 may further display descriptive information 412 of Goal A. Descriptive information 412 may include one or more of Owner, Due Date, Description, Collaborators, Parent goals (See, FIG. 3 ), and Supporting units of work. The Collaborators may be one or more users assigned to work toward the progress. The Supporting work portion may display units of work that are associated with Goal A (e.g., Task X, Task Z, Project W). Completion of such units of work may facilitate, but not directly affect, progress toward fulfillment of Goal A. Each of sub-goals 408 may include an individual status indicator and owner. Upon selection of one of the sub-goals of sub-goals 408 (e.g., Sub-Goal C), a user interface, similar to user interface 400, may display a view showing Sub-Goal C and objective information and descriptive information thereof. The user interface 400 may be referred to as a Business Objective Page within a collaboration environment.

It is noted that FIGS. 3-4 are for illustrative purposes only and are not to be considered limiting. Instead, it is to be understood that user interfaces may be configured in other ways and/or including other elements in accordance with one or more implementations of the system 100 presented herein.

Referring back to FIG. 1 , in some implementations, server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 116 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via some other communication media.

A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resources 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 126 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 116 and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 130 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 130 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 130 may be configured to execute components 108, 110, 112, 114, and/or other components. Processor(s) 130 may be configured to execute components 108, 110, and/or 112, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 130. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, and/or 112 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 130 includes multiple processing units, one or more of components 108, 110, and/or 112 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, and/or 112 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, and/or 112 may provide more or less functionality than is described. For example, one or more of components 108, 110, and/or 112 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, and/or 112. As another example, processor(s) 130 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, and/or 112.

FIG. 2 illustrates a method 200 to characterize units of work based on business objectives, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may define units of work assigned to individual users within the collaboration environment and business objectives associated with the units of work. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.

An operation 204 may obtain progress information and/or other information for individual ones of the business objectives. The progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. A connection between the set of units of work and a corresponding business objective may be indirect in that completion of at least one of the units of work may have no direct impact on the progress toward fulfillment of the corresponding business objective. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to progress component 110, in accordance with one or more implementations.

An operation 206 may update the objective records and/or the other records. The update may be based on the progress information and/or other information. As such, the progress of the business objectives may be maintained by the objective records. Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to progress component 110, in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation. 

What is claimed is:
 1. A system configured to characterize units of work based on objectives, the system comprising: one or more physical processors configured by machine-readable instructions to: manage, at a server, electronically stored environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the users interacting with the collaboration environment via remotely located client computing platforms communicating with the server over one or more Internet connections, the environment state information including a set of work unit records and an objective record, the set of work unit records describing a set of units of work assigned to one or more of the users within the collaboration environment, the objective record describing an objective associated with the set of units of work, the objective comprising an expectation of outcome derived from an event which is external to the collaboration environment, the objective record identifying the set of work unit records by virtue of the set of units of work being associated with the objective; establish an Internet connection between the server and a remotely located client computing platform associated with a user; effectuate communication of information from the server to the remotely located client computing platform via the Internet connection so that the remotely located client computing platform presents a user interface of the collaboration environment through which the user interacts with the collaboration environment, wherein the user interacts with the collaboration environment by providing user input into the user interface indicating progress toward fulfillment of the objective; monitor, by the server, the environment state information to determine updates to the environment state information that impact the progress toward fulfillment of the objective; determine, at the server and based on monitoring the environment state information, progress information for the objective, the progress information conveying the progress toward fulfillment of the objective, wherein a connection between the set of units of work and the objective is indirect in that completion of at least one unit of work in the set of units of work has no direct impact on the progress toward fulfillment of the objective because the progress toward fulfillment of the objective is based on progress toward occurrence of the event which is external to the collaboration environment; and update, at the server, the objective record based on the progress information so that the progress toward fulfillment of the objective is maintained by the objective record.
 2. The system of claim 1, wherein the progress toward fulfillment of the objective is specified as a quantitative value.
 3. The system of claim 2, wherein the quantitative value is a percentage of completion of the objective.
 4. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: effectuate presentation of a view of the objective record in the user interface of the collaboration environment, the view including: a description of the objective; a representation of the set of units of work associated with the objective; and a status indicator for the objective conveying the progress toward fulfillment of the objective.
 5. The system of claim 1, wherein a unit of work in the set of units of work is a project associated with a set of tasks.
 6. The system of claim 1, wherein a unit of work in the set of units of work is a task comprising one or more actions an individual user is expected to accomplish.
 7. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: monitor, by the server over an other Internet connection, an external resource associated with the event; determine, based on monitoring the external resource, the progress toward the occurrence of the event; and determine the progress information further based on the progress toward the occurrence of the event.
 8. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: determine when the progress toward fulfillment of the objective is at or below a progress threshold; correlate occurrence of the progress toward fulfillment being at or below the progress threshold with one or more units of work in the set of units of work; and generate and present a notification including an identification of the one or more of units of work correlated with the occurrence of the progress toward fulfillment being at or below the progress threshold.
 9. The system of claim 1, wherein the objective record is included in an objective record hierarchy such that the objective record is subordinate to a second objective record.
 10. The system of claim 9, wherein the second objective record is included an in a second objective record hierarchy such that the second objective record is subordinate to a third objective record.
 11. A method to characterize units of work based on objectives, the method being implemented in a computer system comprising one or more physical processors configured by machine-readable instructions, such that execution of the machine-readable instructions causes the one or more physical processors to perform the method comprising: managing, at a server, electronically stored environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the users interacting with the collaboration environment via remotely located client computing platforms communicating with the server over one or more Internet connections, the environment state information including a set of work unit records and an objective record, the set of work unit records describing a set of units of work assigned to one or more of the users within the collaboration environment, the objective record describing an objective associated with the set of units of work, the objective comprising an expectation of outcome derived from an event which is external to the collaboration environment, the objective record identifying the set of work unit records by virtue of the set of units of work being associated with the objective; establishing an Internet connection between the server and a remotely located client computing platform associated with a user; effectuating communication of information from the server to the remotely located client computing platform via the Internet connection so that the remotely located client computing platform presents a user interface of the collaboration environment through which the user interacts with the collaboration environment, wherein the user interacts with the collaboration environment by providing user input into the user interface indicating progress toward fulfillment of the objective; monitoring, by the server, the environment state information to determine updates to the environment state information that impact the progress toward fulfillment of the objective; determining, at the server and based on the monitoring the environment state information, progress information for the objective, the progress information conveying the progress toward fulfillment of the objective, wherein a connection between the set of units of work and the objective is indirect in that completion of at least one unit of work in the set of units of work has no direct impact on the progress toward fulfillment of the objective because the progress toward fulfillment of the objective is based on progress toward occurrence of the event which is external to the collaboration environment; and updating, at the server, the objective record based on the progress information so that the progress toward fulfillment of the objective is maintained by the objective record.
 12. The method of claim 11, wherein the progress toward fulfillment of the objective is specified as a quantitative value.
 13. The method of claim 12, wherein the quantitative value is a percentage of completion of the objective.
 14. The method of claim 11, further comprising: effectuating presentation of a view of the objective record in the user interface of the collaboration environment, the view including: a description of the objective; a representation of the set of units of work associated with the objective; and a status indicator for the objective conveying the progress toward fulfillment of the objective.
 15. The method of claim 11, wherein a unit of work in the set of units of work is a project associated with a set of tasks.
 16. The method of claim 11, wherein a unit of work in the set of units of work is a task comprising one or more actions an individual user is expected to accomplish.
 17. The method of claim 11, further comprising: monitoring, by the server over an other Internet connection, an external resource associated with the event; determining, based on the monitoring the external resource, the progress toward the occurrence of the event; and determining the progress information further based on the progress toward the occurrence of the event.
 18. The method of claim 11, further comprising: determining when the progress toward fulfillment of the objective is at or below a progress threshold; correlating occurrence of the progress toward fulfillment being at or below the progress threshold with one or more units of work in the set of units of work; and generating and presenting a notification including an identification of the one or more of units of work correlated with the occurrence of the progress toward fulfillment being at or below the progress threshold.
 19. The method of claim 11, wherein the objective record is included in an objective record hierarchy such that the objective record is subordinate to a second objective record.
 20. The method of claim 19, wherein the second objective record is included an in a second objective record hierarchy such that the second objective record is subordinate to a third objective record. 